Travel Notifications API
Technical Notes
/connex/travel-notifications
- Both the ATM Locator or Connex Travel Notifications use a back-end API which involves an extra step of acquiring an authorization key as well as configuring client IP addresses.
- The Travel Notifications process is not in real-time, so an immediate update may not be visible after submission.
Falcon and Authorization Blocks
- Falcon Travel Notifications allow members to provide you with travel information including name, telephone numbers, and travel destinations with start and end dates. You can assign individualized blocking instructions to use in the event the cardholder cannot be reached to confirm potentially suspicious card usage. This feature works in conjunction with FalconTM Fraud Manager, 24/7 Falcon Case Management services, and Fraud Navigator Authorization Blocks.
- VIP Authorization Block Bypass can exempt elite cardholders from all authorization blocks during specified time periods. Authorization blocks are used in response to new fraud threats to immediately deny all transactions meeting certain criteria. This feature allows these blocks to be bypassed for specific cardholders. Participation in Falcon is not required.
- An active Falcon Travel Notification will exempt a card from both Real-time Decisioning in Falcon and Authorization Blocks initiated in Fraud Navigator.
Contact Reason Table for Travel Notifications API
Authorized Contacts may be required for both endpoints - /connex/travel-notifications & /connex/travel-notifications.get - with the Contact Reason ID described below surrounding cardholder contact.
| Contact Reason ID | Description |
|---|---|
| 1 | Cardholder is minor |
| 2 | Cardholder travels within U.S. but outside home state frequently |
| 3 | Cardholder is stationed outside of U.S. or travels internationally frequently |
| 4 | Cardholder is hearing impaired |
| 5 | Cardholder has established Power of Attorney |
| 6 | Other |
Block Codes Table for Travel Notifications API
Blocking Instructions are required for the endpoint - /connex/travel-notifications. The following Blocking Codes are used when setting Travel Notifications - which note whether or not to contact the cardholder.
| Block Code | Description    |
|---|---|
| BI01 | Place Blocks according to normal operating procedures |
| BI02 | Call Cardholder, but Do Not Block if the transaction origin and date are consistent with the travel plans |
| BI03 | Never block regardless of the score or risk |
| BI04 | Do Not Call Cardholder. Do Not Block if the transaction origin and date are consistent with travel plans |
Exceptions Messages for Travel Notifications/Conierge APIs
Each API call returns a response that indicates success or failure. A failed status includes one or more exception codes. For exceptions related to the detail information submitted for a travel notification, the placeholder {i} shown below is replaced with a number to indicate which detail record caused the exception.
API Call Exceptions
| API Call | Exceptions |
|---|---|
| 1001 | Invalid mime-type. Available mime-types: application/json |
| 1002 | The version header is missing from the request. |
| 1003 | Invalid version number. Available versions: 1 |
| 1004 | Invalid HTTPS method. Available methods: Post |
| 1005 | The authorization header is missing from the request. |
| 1006 | The API key is not valid for this service. |
| 1007 | This service cannot be accessed from your current IP address. |
| 1008 | A problem occurred while processing the request. |
Data Exceptions
| Data | Exceptions |
|---|---|
| 2001 | Notification, inquiry criteria, or cancellation criteria cannot be found in the request. |
| 2002 | The provided data format is invalid. |
| 2003 | VIP or RTN is missing. |
| 2004 | VIP or RTN is invalid. For VIP, the value must be Y or N. |
| 2005 | Institution R&T number or cardholder card number is missing. |
| 2006 | Cardholder card number is invalid. |
| 2007 | Cardholder first name is missing, or RTN cannot be found using the provided API key. |
| 2008 | Cardholder last name is missing, or the provided RTN does not match the RTN assigned to your API key. |
| 2009 | Cardholder primary phone or detail ID is missing. |
| 2010 | Cardholder primary phone type or detail ID is missing or invalid. |
| 2011 | Alternate contact first name is missing. |
| 2012 | Alternate contact last name is missing. |
| 2013 | Alternate contact phone is missing. |
| 2014 | Authorized contact first name is missing. |
| 2015 | Authorized contact last name is missing. |
| 2016 | Authorized contact phone is missing. |
| 2017 | A VIP notification cannot have a blocking instruction. |
| 2018 | Blocking instructions code is missing. |
| 2019 | Blocking instructions call cardholder is missing. |
| 2020 | A VIP notification cannot have a CU contact. |
| 2021 | CU contact name value is missing. |
| 2022 | CU contact phone value is missing. |
| 2023 | CU contact email value is missing. |
| 2024 | Detail {i} from date is missing. |
| 2025 | Detail {i} to date is missing. |
| 2026 | Detail {i} country is missing. |
| 2027 | Detail {i} purpose is missing. |
| 2028 | Institution R&T Number is invalid. |
| 2029 | Cardholder card number is invalid. |
| 2030 | Cardholder plastic number is invalid. Length cannot exceed 10 characters. |
| 2031 | Cardholder first name is invalid. Length cannot exceed 25 characters. |
| 2032 | Cardholder last name is invalid. Length cannot exceed 25 characters. |
| 2033 | Cardholder primary phone is invalid. Length must be 10 to 14 characters. |
| 2034 | Cardholder primary phone type is invalid. |
| 2035 | Cardholder secondary phone is invalid. Length must be 10 to 14 characters. |
| 2036 | Cardholder secondary phone type is invalid. |
| 2037 | Cardholder email is invalid. The value must be a valid format and not exceed 100 characters. |
| 2038 | Cardholder shared card is invalid. The value must be Y or N. |
| 2039 | Alternate contact first name is invalid. Length cannot exceed 25 characters. |
| 2040 | Alternate contact last name is invalid. Length cannot exceed 25 characters. |
| 2041 | Alternate contact phone is invalid. Length must be 10 to 14 characters. |
| 2042 | Alternate contact email is invalid. The value must be a valid format and not exceed 100 characters. |
| 2043 | Authorized contact first name is invalid. Length cannot exceed 25 characters. |
| 2044 | Authorized contact last name is invalid. Length cannot exceed 25 characters. |
| 2045 | Authorized contact phone is invalid. Length must be 10 to 14 characters. |
| 2046 | Authorized contact relationship to cardholder is invalid. Length cannot exceed 100 characters. |
| 2047 | Authorized contact reason id is invalid. |
| 2048 | Authorized contact other reason description is invalid. Length cannot exceed 100 characters. |
| 2049 | Blocking instructions code is invalid. |
| 2050 | Blocking instructions call cardholder is invalid. The value must be Y or N. |
| 2051 | Blocking instructions comment is invalid. Length cannot exceed 1000 characters. |
| 2052 | CU contact name is invalid. Length cannot exceed 100 characters. |
| 2053 | CU contact phone is invalid. Length cannot exceed 14 characters. |
| 2054 | CU contact extension is invalid. Length cannot exceed 6 characters. |
| 2055 | CU contact email is invalid. |
| 2056 | Detail {i} travel from date is invalid. Value must be a valid date. |
| 2057 | Detail {i} travel to date is invalid. Value to date must be a valid date. |
| 2058 | Detail {i} state is invalid. |
| 2059 | Detail {i} country is invalid. |
| 2060 | Detail {i} phone is invalid. |
| 2061 | Detail {i} purpose is invalid. |
| 2062 | Detail {i} note is invalid. Length cannot exceed 1000 characters. |